Dec 01 23:11:05.741 INFO testing bionikspoon/minigrep against master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61 for beta-1.31-5
Dec 01 23:11:05.741 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-3/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 23:11:06.115 INFO [stdout] 501f1da3c18be9339441d95567b5059a27e2a1e8463934ac9aeeab95dbe1ec81
Dec 01 23:11:06.120 INFO running `"docker" "start" "-a" "501f1da3c18be9339441d95567b5059a27e2a1e8463934ac9aeeab95dbe1ec81"`
Dec 01 23:11:07.443 INFO [stderr] usermod: no changes
Dec 01 23:11:07.503 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 23:11:07.503 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 23:11:07.503 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 23:11:07.503 INFO [stderr] files will be included as a binary target:
Dec 01 23:11:07.503 INFO [stderr] 
Dec 01 23:11:07.503 INFO [stderr] * /source/src/main.rs
Dec 01 23:11:07.503 INFO [stderr] 
Dec 01 23:11:07.503 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 23:11:07.503 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 23:11:07.503 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 23:11:07.503 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 23:11:07.503 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 23:11:07.503 INFO [stderr] 
Dec 01 23:11:07.503 INFO [stderr] For more information on this warning you can consult
Dec 01 23:11:07.503 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 23:11:07.503 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `minigrep`,
Dec 01 23:11:07.503 INFO [stderr] please set bin.path in Cargo.toml
Dec 01 23:11:07.503 INFO [stderr]    Compiling minigrep_lib v0.1.0 (/source)
Dec 01 23:11:09.334 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.85s
Dec 01 23:11:09.337 INFO [stderr] su: No module specific data is present
Dec 01 23:11:10.111 INFO running `"docker" "inspect" "501f1da3c18be9339441d95567b5059a27e2a1e8463934ac9aeeab95dbe1ec81"`
Dec 01 23:11:10.420 INFO running `"docker" "rm" "-f" "501f1da3c18be9339441d95567b5059a27e2a1e8463934ac9aeeab95dbe1ec81"`
Dec 01 23:11:10.740 INFO [stdout] 501f1da3c18be9339441d95567b5059a27e2a1e8463934ac9aeeab95dbe1ec81
Dec 01 23:11:10.747 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-3/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 23:11:11.159 INFO [stdout] 75a8102f8182a79860cda1a9cba5c7cc99f9ca7d57663ef3291be5c562222d0a
Dec 01 23:11:11.167 INFO running `"docker" "start" "-a" "75a8102f8182a79860cda1a9cba5c7cc99f9ca7d57663ef3291be5c562222d0a"`
Dec 01 23:11:12.435 INFO [stderr] usermod: no changes
Dec 01 23:11:12.503 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 23:11:12.503 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 23:11:12.503 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 23:11:12.503 INFO [stderr] files will be included as a binary target:
Dec 01 23:11:12.503 INFO [stderr] 
Dec 01 23:11:12.503 INFO [stderr] * /source/src/main.rs
Dec 01 23:11:12.503 INFO [stderr] 
Dec 01 23:11:12.503 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 23:11:12.503 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 23:11:12.503 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 23:11:12.503 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 23:11:12.503 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 23:11:12.503 INFO [stderr] 
Dec 01 23:11:12.503 INFO [stderr] For more information on this warning you can consult
Dec 01 23:11:12.503 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 23:11:12.503 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `minigrep`,
Dec 01 23:11:12.503 INFO [stderr] please set bin.path in Cargo.toml
Dec 01 23:11:12.510 INFO [stderr]    Compiling minigrep_lib v0.1.0 (/source)
Dec 01 23:11:14.987 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.52s
Dec 01 23:11:14.987 INFO [stderr] su: No module specific data is present
Dec 01 23:11:15.484 INFO running `"docker" "inspect" "75a8102f8182a79860cda1a9cba5c7cc99f9ca7d57663ef3291be5c562222d0a"`
Dec 01 23:11:15.853 INFO running `"docker" "rm" "-f" "75a8102f8182a79860cda1a9cba5c7cc99f9ca7d57663ef3291be5c562222d0a"`
Dec 01 23:11:16.122 INFO [stdout] 75a8102f8182a79860cda1a9cba5c7cc99f9ca7d57663ef3291be5c562222d0a
Dec 01 23:11:16.125 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-3/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/beta-1.31-5/master#8940af3cea4a9a9deabcaf843b2f8cad9a83fc61:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +8940af3cea4a9a9deabcaf843b2f8cad9a83fc61-alt test --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 01 23:11:16.603 INFO [stdout] 2c0415803ae985ed745cab26342142b62857eb83bbaedc471dc0b4f04b4a6ce0
Dec 01 23:11:16.611 INFO running `"docker" "start" "-a" "2c0415803ae985ed745cab26342142b62857eb83bbaedc471dc0b4f04b4a6ce0"`
Dec 01 23:11:18.078 INFO [stderr] usermod: no changes
Dec 01 23:11:18.123 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 23:11:18.123 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 23:11:18.123 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 23:11:18.123 INFO [stderr] files will be included as a binary target:
Dec 01 23:11:18.123 INFO [stderr] 
Dec 01 23:11:18.123 INFO [stderr] * /source/src/main.rs
Dec 01 23:11:18.123 INFO [stderr] 
Dec 01 23:11:18.123 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 23:11:18.123 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 23:11:18.123 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 23:11:18.123 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 23:11:18.123 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 23:11:18.123 INFO [stderr] 
Dec 01 23:11:18.123 INFO [stderr] For more information on this warning you can consult
Dec 01 23:11:18.123 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 23:11:18.123 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `minigrep`,
Dec 01 23:11:18.123 INFO [stderr] please set bin.path in Cargo.toml
Dec 01 23:11:18.124 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.02s
Dec 01 23:11:18.143 INFO [stderr]      Running /target/debug/deps/minigrep_lib-805d717ef1fd71c7
Dec 01 23:11:18.151 INFO [stdout] 
Dec 01 23:11:18.151 INFO [stdout] running 2 tests
Dec 01 23:11:18.159 INFO [stdout] test tests::search_has_one_result ... ok
Dec 01 23:11:18.159 INFO [stdout] test tests::case_insensitive ... ok
Dec 01 23:11:18.159 INFO [stdout] 
Dec 01 23:11:18.159 INFO [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 01 23:11:18.159 INFO [stdout] 
Dec 01 23:11:18.159 INFO [stderr]      Running /target/debug/deps/minigrep-06a3532f66f97b50
Dec 01 23:11:18.171 INFO [stdout] 
Dec 01 23:11:18.171 INFO [stdout] running 0 tests
Dec 01 23:11:18.171 INFO [stdout] 
Dec 01 23:11:18.171 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 01 23:11:18.171 INFO [stdout] 
Dec 01 23:11:18.171 INFO [stderr]    Doc-tests minigrep_lib
Dec 01 23:11:18.970 INFO [stdout] 
Dec 01 23:11:18.970 INFO [stdout] running 0 tests
Dec 01 23:11:18.970 INFO [stdout] 
Dec 01 23:11:18.970 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 01 23:11:18.970 INFO [stdout] 
Dec 01 23:11:18.977 INFO [stderr] su: No module specific data is present
Dec 01 23:11:19.835 INFO running `"docker" "inspect" "2c0415803ae985ed745cab26342142b62857eb83bbaedc471dc0b4f04b4a6ce0"`
Dec 01 23:11:20.115 INFO running `"docker" "rm" "-f" "2c0415803ae985ed745cab26342142b62857eb83bbaedc471dc0b4f04b4a6ce0"`
Dec 01 23:11:20.438 INFO [stdout] 2c0415803ae985ed745cab26342142b62857eb83bbaedc471dc0b4f04b4a6ce0
